Memory Requirements by Connection Type
|
ERP or System |
RFgen Server |
Client PerConnection |
Database Connection |
Screen Mapping |
Per ERP Connection |
|
Deltek CostPoint |
15 MB |
10 MB |
10 MB |
NA |
NA |
|
General Connectivity/Legacy Systems |
15 MB |
10 MB |
10 MB |
25 MB |
NA |
|
Oracle E-Business Suite |
15 MB |
10 MB |
10 MB |
NA |
NA |
|
Oracle JD Edwards |
15 MB |
10 MB |
10 MB |
25 MB |
100 MB |
|
Oracle SCM |
15 MB |
10 MB |
NA |
NA |
NA |
|
SAP |
15 MB |
10 MB |
NA |
NA |
30 MB |
Notes:
|
Deltek CostPoint |
Deltek CostPoint uses a Web Service object in place of an ERP Connection and the memory usage by the web service is nominal. |
|
|
|
|
General Connectivity
|
If your data connector is setup for Connection Pooling (a licensed database connection shared by multiple clients), each pooled connection would use approximately 10 megabytes. To estimate your memory requirements, multiply the total number of pooled connections by 10. For example, 5 pooled connections would require approximately 50 megabytes. If Connection Pooling is disabled, each active client would have its own connection, and each connection would use approximately 10 megabytes. To estimate your memory requirements, multiply the total number of client connections by 10. For example, 5 client connections would require approximately 50 megabytes. |
|
Oracle JDE |
If your JDE is setup for Connection Pooling, (a single licensed database connection shared by multiple clients), each pooled connection would use approximately 100 megabytes. To estimate your memory requirements, multiply the total number of pooled connections by 100 megabytes. For example, 5 pooled connections would require about 500 megabytes of memory. If Connection Pooling is disabled, each client would have its own connection, and each connection would use approximately 100 megabytes. To estimate your memory requirements, multiply the total number of client connections by 100 megabytes. For example, 5 client connections would require approximately 500 megabytes of memory. |
|
|
|
|
Oracle EBS |
If your ERP is setup for Connection Pooling (a licensed database connection shared by multiple clients), each pooled connection would use approximately 10 megabytes. To estimate your memory requirements, multiply the total number of pooled connections by 10. For example, 5 pooled connections would require approximately 50 megabytes. If Connection Pooling is disabled, each active client would have its own connection, and each connection would use approximately 10 megabytes. To estimate your memory requirements, multiply the total number of client connections by 10. For example, 5 client connections would require approximately 50 megabytes. |
|
|
|
|
Oracle SCM Cloud |
If your data connector is setup for Connection Pooling (a licensed database connection shared by multiple clients), each pooled connection would use approximately 10 megabytes. To estimate your memory requirements, multiply the total number of pooled connections by 10. For example, 5 pooled connections would require approximately 50 megabytes. If Connection Pooling is disabled, each active client would have its own connection, and each connection would use approximately 10 megabytes. To estimate your memory requirements, multiply the total number of client connections by 10. For example, 5 client connections would require approximately 50 megabytes. |
|
|
|
|
SAP |
If SAP is setup for Connection Pooling (a licensed database connection shared by multiple clients), each pooled connection would use approximately 30 megabytes. To estimate your memory requirements, multiply the total number of pooled connections by 30. For example, 5 pooled connections would require approximately 150 megabytes. If Connection Pooling is disabled, each active client would have its own connection, and each connection would use approximately 30 megabytes. To estimate your memory requirements, multiply the total number of client connections by 30. For example, 5 client connections would require approximately 150 megabytes. |